Methods of transmitting data blocks in wireless communication system

ABSTRACT

Disclosed is a method for generating a data block to be transmitted from a specific layer in a transmitting side to a receiving side in a wireless communication system. The method includes receiving an upper layer datei block from an upper layer and generating a lower layer data block including at least part of the upper layer data block and state indication information indicating a state of the upper layer data block, the state indication information being selected variably according to a logical channel through which the upper layer data block is received. This method optimizes overhead of a header of each upper layer data block according to contents of the upper layer data block and event situations associated with the upper layer data block, thereby increasing system efficiency.

This application claims priority to is a reissue of, and claims the benefit of, U.S. Pat. No. 8,081,662, issued on Dec. 20, 2011, which is a 35 U.S.C. §371 National Stage Entry of International Application No. PCT/KR2008/002468 filed on Apr. 30, 2008, which claims priority to U.S. Provisional Application No. 60/915,042 filed on Apr. 30, 2007, U.S. Provisional Application No. 60/915,417, filed May 1, 2007 and Korean Patent Application No. 10-2008-0040506, filed on Apr. 30, 2008, all of which are incorporated by reference for all purposes as if fully set forth herein.

TECHNICAL FIELD

The present invention relates to a wireless communication system, and more particularly, to a method for transmitting data blocks in a wireless communication system.

BACKGROUND ART

FIG. 1 illustrates the structure of a wireless access protocol responsible for data transmission in a radio link of a Universal Mobile Telecommunication System (UMTS) which is a third generation mobile communication system. Data link layers corresponding to the second layer (Layer 2: L2) of the Open System Interconnection (OSI) reference model include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, and a Broadcast/Multicast Control (BMC) layer. The physical layer corresponds to the first layer (Layer 1: L1). Information exchange between protocol layers is performed through virtual access points that are referred to as “Service Access Points (SAPS)”, which are represented by ovals in FIG. 1. Data units communicated between layers are given different names. These data units are referred to as “Service Data Units (SDUs)” and basic units that protocols use for transmitting data are referred to as “Protocol Data Units (PDUs)”. In the following description of the invention, data delivered between layers in the wireless access protocol structure indicates data blocks in specific units such as SDUs or PDUs described above.

The MAC layer is a layer responsible for mapping between logical and transport channels. The MAC layer selects an appropriate transport channel for transmitting data received from the RLC layer and adds required control information to a header of a MAC PDU. Special functions performed by the MAC layer include a radio resource management function and a measurement function. The radio resource management function is not performed solely by the MAC layer. Instead, the radio resource management function serves to set operations of the MAC layer based on various MAC parameters received from a Radio Resource Control (RRC), which is located above the MAC layer, to control data transmission. Examples of the radio resource management function include a function to change mapping relations between logical and transport channels or to multiplex and transmit data through a scheduling function. The measurement function is to measure the amount of traffic of a terminal and to report the measurement to an upper layer. The upper layer can change the configuration (or setting) of the MAC layer based on the measurement information obtained by the MAC layer of the terminal, thereby efficiently managing radio (wireless) resources.

The RLC layer is located above the MAC layer and supports reliable data transmission. The RLC layer segments and concatenates RLC Service Data Units (SDUs) received from the above layer in order to construct data having a size suitable for a radio link. An RLC layer at the receiving side supports data recombination in order to restore original RLC SDUs from the received RLC PDUs. Each RLC entity can operate in a Transparent Mode (TM), an Unacknowledged Mode (UM), or an Acknowledged Mode (AM) according to processing and transmission methods of RLC SDUs. When the RLC entity operates in the TM, it transfers an RLC SDU received from an upper entity or layer to the MAC layer without adding any header information to the RLC SDU. When the RLC entity operates in the UM, it segments/concatenates RLC SDUs to construct RLC PDUs and adds header information including a sequence number to each RLC PDU. However, in the UM, the RLC entity does not support data retransmission. When the RLC entity operates in the AM, it can use the RLC SDU segmentation/concatenation function to construct RLC PDUs and can perform retransmission when packet transmission has failed. Various parameters and variables such as a transmission window, a reception window, a timer, and a counter are used for the retransmission function in the AM.

The PDCP layer is used only in packet exchange regions and can compress and transmit IP packet headers so as to increase the transmission efficiency of packet data in wireless channels. The PDCP layer also manages sequence numbers in order to prevent data loss during Serving RNC (SRNC) relocation.

The BMC layer broadcasts cell broadcast messages received from a core network to multiple users through a common channel.

The physical layer, which is the first layer, provides an information transfer service to an upper layer using a physical channel. The physical layer is connected to the Media Access Control (MAC) layer located above the physical layer through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. Data is transferred between different physical layers (specifically, physical layers of transmitting and receiving sides) through a physical channel.

A Radio Resource Control (RRC) layer, which is the third layer located at the bottom, is defined only in the control plane and is responsible for controlling logical, transport, and physical channels in association with configuration, re-configuration, and release of Radio Bearers (RBs). RBs are services that the second layer provides for data communication between terminals and a network including a base station. The control plane is a hierarchy in which control information is transferred in the vertical structure of the wireless access protocol of FIG. 1 and the user plane is a hierarchy in which user information such as data/information is transferred.

As shown in FIG. 1, an RLC PDU generated in the RLC layer is transferred to the MAC layer and is handled as a MAC SDU in the MAC layer. While a MAC SDU, which is an RLC PDU received from the RLC layer, undergoes various functions of the MAC layer, various header information required for data processing is added to the MAC SDU. The header information can be altered depending on mapping relations between logical and transport channels.

Logical channels provide transport passages required for data exchange between the MAC and the RLC layer. Each logical channel is classified into control and traffic channels according to the type of data transmitted therethrough. The control channel transmits data of the control plane and the traffic channel transmits user traffic data. A logical channel is a type of data stream carrying a specific type of information. Each logical channel is generally connected to one RLC entity. One or more logical channels of the same type can also be connected to an RLC entity. Transport channels provide passages for data communication between the physical and MAC layers. A data stream in a logical channel is embodied as a MAC PDU in the MAC layer. Reference will now be made to the MAC PDU.

FIG. 2 illustrates an example structure of a MAC PDU with a header added thereto in a mobile communication system. A MAC PDU includes one or more MAC SDUs corresponding to payload for data and a MAC header which is a set of MAC sub-headers indicating the size or type of each MAC SDU. In the example of FIG. 2, it is assumed that a total of N upper layer data blocks are provided. A MAC sub-header includes a Logical Channel ID (LCID) identifying each SDU, a length field (L) indicating the size of each SDU, and an extension field (E) indicating whether a subsequent field is a MAC header or an SDU to indicate whether or not additional headers are present.

The LCID indicates which logical channel corresponds to data of a MAC SDU which is an upper layer data block associated with a sub-header including the LCID. That is, one MAC PDU includes one or more upper layer data blocks and different logical channels can be allocated to the upper layer data blocks individually.

Generally, one or more logical channels can be established between a terminal and a base station. For example, in the case of a voice service, not only a logical channel carrying voice traffic but also a logical channel for a Signaling Radio Bearer (SRB) for control information communicated between the base station and the terminal can be established between the base station and the terminal. In this case, state changes of the SRB and state changes of the voice traffic channel may occur independently of each other. More specifically, change of an Adaptive Multi-Rate (AMR) codec mode in the voice traffic channel and generation of an urgent message in the SRB channel may occur independently of each other. Therefore, an upper layer data block for voice traffic and an upper layer data block for an SRB can both be allocated to one MAC PDU and the size or the like of each upper layer data block can be set to be different according to the type and usage of a logical channel associated with the upper layer data block. The size of each upper layer data block can be set through a size field in a MAC sub-field of a MAC SDU corresponding to the upper layer data block.

DISCLOSURE Technical Problem

Since MAC header values, which are part of a MAC PDU (i.e., a lower layer data block) excluding MAC SDUs (i.e., upper layer data blocks) containing payload, are not actual data values as described above, it is necessary to minimize the MAC header values to increase throughput. However, the sizes or types of the fields of the MAC header are fixed and used regardless of which logical channel is associated with each MAC SDU in the MAC PDU, regardless of what are actual contents of the MAC SDU, etc. This causes a reduction in system efficiency due to overhead of control signals.

It is also necessary to allocate radio resources to the upper layer data block suitable for characteristics of the upper layer data block and to perform an operation on the upper layer data block according to urgency and importance of the processing of upper layer data block.

The present invention has been suggested to overcome the above problems in the background art, and it is an object of the present invention to provide a method for generating a data block in a communication system.

Another object of the present invention is to provide a method for generating a data block using state indication information of one or more upper layer data blocks in a communication system.

Technical Solution

In an aspect of the invention, there is provided a method for generating a data block to be transmitted from a specific layer in a transmitting side to a receiving side in a wireless communication system. This method includes receiving an upper layer data block from an upper layer, and generating a lower layer data block including at least part of the upper layer data block and state indication information indicating a state of the upper layer data block, the state indication information being selected variably according to a logical channel through which the upper layer data block is received.

In another aspect of the invention, there is provided a data block structure transmitted from a specific layer in a transmitting side to a receiving side in a wireless communication system. The data block structure includes a first field including an identifier of a logical channel through which an upper layer data block is received, a second field including state indication information indicating a state of the upper layer data block received from an upper layer, the state indication information being selected variably according to the logical channel through which the upper layer data block is received, and at least part of the upper layer data block.

Advantageous Effects

The method for generating a data block in a wireless communication system according to the invention provides the following advantages.

First, the overhead of a header of each upper layer data block is optimized according to contents of the upper layer data block and event situations associated with the upper layer data block, thereby increasing system efficiency.

Second, the receiving side of the upper layer data block can efficiently manage radio resources using the state indication information.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates the structure of a wireless access protocol responsible for data transmission in a radio link of a Universal Mobile Telecommunication System (UMTS) which is a third generation mobile communication system.

FIG. 2 illustrates an example structure of a MAC PDU with a header added thereto in a mobile communication system.

FIG. 3 illustrates a structure of a network in an E-UMTS system in the related art.

FIG. 4 illustrates example transmission of a full header packet and a compressed header packet when a conventional header compression scheme is employed.

FIG. 5 illustrates a MAC PDU including at least one state indication information suggested in another embodiment of the invention.

FIG. 6 illustrates an example structure of a MAC PDU in an E-UMTS suggested in another embodiment of the invention.

MODE FOR INVENTION

The above and other configurations, operations, and features of the present invention will be more easily understood from the embodiments of the invention described with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention, rather than to show the only embodiments that can be implemented according to the invention. The embodiments described below are examples wherein the technical features of the invention are applied to an Evolved Universal Mobile Telecommunications System (E-UMTS) that is also called a “Long Term Evolution (LTE) system”. It is apparent that the technical features of the invention can also be applied to other similar mobile communication systems such as IEEE 802.16m or Wibro systems.

The E-UMTS system is an evolved version of the conventional WCDMA UMTS system and a basic standardization process thereof is in progress in the 3rd Generation Partnership Project (3GPP). For details of the technical specification of UMTS and E-UMTS, see Release 7, Release 8, and Release 9 of “3rd Generation Partnership Project; Technical Specification Group Radio Access Network”.

The technology described below can be used for various communication systems including a system using multiple antennas.

Communication systems are widely disposed to provide various communication services such as voice and packet data services. This technology can be used for downlink or uplink. The term “downlink” refers to communication from a base station to a terminal and “uplink” refers to communication from a terminal to a base station. The term “base station” generally refers to a fixed point that communicates with terminals and includes a network excluding terminals in a communication system including not only a physical transport end but also upper layers. Thus, in the invention, the network and base station are considered identical as they constitute the side opposite the terminals. Terminals may be fixed or mobile. The invention can be used in a single-carrier or multi-carrier communication system. The multi-carrier system can use Orthogonal Frequency Division Multiplexing (OFDM) or other multi-carrier modulation techniques.

FIG. 3 illustrates a structure of a network in the E-UMTS system.

The E-UMTS network can be mainly divided into an E-UTRAN and a CN. The E-UTRAN includes terminals (or User Equipments (UEs)), base stations (or eNode Bs (eNBs)), a Serving Gateway (S-GW) located at an end of the network and connected to an external network, and a Mobility Management Entity (MME) that manages mobility of UEs. One eNB may have one or more cells. eNBs are connected to each other through an X2 interface. Each eNB is connected to UEs through a radio interface and is connected to an Evolved Packet Core (EPC) through an S1 interface.

An embodiment of the invention suggests a method for generating data blocks to be transferred to a lower layer using state indication information indicating occurrence of a specific event associated with at least one upper layer data block to be transferred to a MAC layer and the type of a logical channel associated with the at least one upper layer data block.

The specific event suggested in the embodiment of the invention indicates occurrence, change, or removal of a specific situation associated with at least one of the type and contents of a logical channel carrying the upper layer data block.

The specific event may be set for each logical channel. The logical channel may be any type of logical channel such as a channel indicating system control information, a channel carrying paging (or call) information of a terminal, a channel for dedicated control information between a terminal and a base station, a channel for common control information, a channel for dedicated traffic for a specific terminal, and a channel for common traffic.

State indication information suggested in an embodiment of the invention indicates the occurrence or nonoccurrence of the specific event associated with a logical channel identified by an identifier of an upper layer data block included in a MAC header. More specifically, the MAC layer can receive an LCID that serves as an identifier of an upper layer data block for the same type of service from an upper layer and can determine which logical channel corresponds to the upper layer data block and can receive, from the upper layer, information indicating whether or not a specific situation associated with the logical channel has occurred or can determine the size or the like of radio resources required by the MAC layer to determine the value of the state indication information.

The state indication information may be one or more bits long. The number of bits of the state indication information is determined according to the number of specific events associated with the logical channel identified by the LCID. More specifically, 1 bit suffices for the state indication information if the number of specific events associated with the logical channel is 2 and 2 bits suffice if the number of specific events is 4. The number of bits of the state indication information can be changed according to the system operating mode.

A specific event for setting the state indication information suggested in an embodiment of the invention is an occasion where the upper layer data block is a voice data block. This informs the MAC layer or the receiving side of facts such as the fact that real-time processing is required and a relatively low amount of radio resources suffices compared to when the upper layer data block associated with the specific logical channel is a non-voice data block. This enables appropriate radio resource allocation.

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where the upper layer data block is a silent data block. This increases the efficiency of resource management in a system that allocates radio resources in units of milliseconds or tens of milliseconds (possibly, in other units smaller than milliseconds or greater than tens of milliseconds) since the minimum amount of radio resources for maintaining call connection is required in the case where the upper layer data block is a silent data block.

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where the upper layer data block is an RRC control message data block. Examples of the RRC control message include system information and RRC connection request, establishment, and release-related messages. The MAC layer or receiving side determines the priority of processing of the upper layer data block and the amount of radio resources required for the upper layer data block according to the type of the RRC control message.

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where the upper layer data block is a Non Access Stratum (NAS) control message data block. The MAC layer or receiving side determines the priority of processing of the upper layer data block and the amount of radio resources required for the upper layer data block according to the system operating mode since the NAS control message includes protocols associated with signaling between UEs and a core network.

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where the upper layer data block is associated with a full header data block or a compressed header data block. As described above, the PDCP layer located above the MAC layer compresses header information of an IP-based data stream such as Transmission Control Protocol (TCP)/Internet Protocol (IP) or Routing Table Protocol (RTP)/User Datagram Protocol (UDP)/IP to increase data transmission efficiency. More specifically, header compression is performed to increase transmission efficiency of IP packet data which is a data block in a wireless channel since the size of a header of an IP packet used in a wired network covers a significant proportion of the overall size of the IP packet. Header compression is based on the fact that each of the headers of packets belonging to the same packet stream has a large constant portion. Header compression is a method for reducing the overhead of headers by storing constant fields in context format in both a compressor of the transmitting side and a decompressor of the receiving side and then transmitting only changed fields after the context is created.

A PDCP entity of the transmitting side receives a PDCP SDU from an upper layer and compresses header information of the corresponding packet using a unique header compression scheme to construct a PDCP PDU and then transfers the PDCP PDU to the RLC layer.

FIG. 4 illustrates example transmission of a full header packet and a compressed header packet when a conventional header compression scheme is employed. In the following description, packets associated with header compression indicate IP-based data packets such as TCP/IP packets.

At an initial stage of header compression of a packet stream, header compression provides no benefit since the compressor transmits a full header packet to form context of the packet stream. However, after context is created, header compression provides significant benefits since the compressor transmits only compressed header packets. Which packet is to be transmitted with a full header and which packet is to be transmitted with a compressed header is determined solely by the compressor. Generally, a full header packet is transmitted when context of a packet stream is initially created and, thereafter, a full header packet is transmitted each time a predetermined time elapses while compressed header packets are transmitted so that context of the decompressor is synchronized with context of the compressor.

Upon receiving a packet from an upper layer, a PDCP compressor in a transmitting side transmits the packet together with a full or compressed header to a receiving side according to the pattern of the header of the packet. The compressor transmits the packet as a full header packet if it determines that it is necessary to create new context or update context and transmits the packet as a compressed header packet if it determines that context of the header pattern of the packet has already been created in the decompressor.

The PDCP decompressor in the receiving side needs to receive a full header packet of a packet stream to create corresponding context because the context is a basis for recovering compressed headers that will be received afterwards. If the decompressor receives a compressed header packet before context has been created, the compressor discards the received packet since it cannot reconstruct the original header of the packet.

More specifically, when a header compression scheme is used for a PS service in a radio link, the transmitting-side PDCP transmits each packet, received in a stream having the same Quality of Service (QoS) from an upper layer, as one of a packet that serves to create or update context or a packet that does not serve to create or update context. The packet that serves to create or update context can be considered much more important than the packet that does not serve to create or update context since all packets that are not to create or update context, subsequent to a packet that serves to create or update context, will be discarded without being decompressed at the receiving side if the packet that serves to create or update context has not been successfully received by the receiving side.

Therefore, the MAC layer or the receiving side is previously informed whether or not a header of an upper layer data block associated with a common or dedicated traffic channel has been compressed, thereby allowing the MAC layer or the receiving side to determine the priority of processing of the upper layer data block, the importance of the processing, the amount of radio resources that should be secured, and the like.

Table 1 illustrates an example where an LCID serving as an identifier of an upper layer data block indicates a logical channel associated with a dedicated or common traffic channel and a 2-bit state indication information indicates whether or not compression of a header has occurred as an event associated with the logical channel according to another embodiment of the invention.

TABLE 1 STATE INDICATION INFORMATION HEADER OF CURRENT OR NEXT (2 BITS) UPPER LAYER DATA BLOCK 0b00 currently transmitted upper layer data block has full header 0b01 currently transmitted upper layer data block has compressed header 0b10 next upper layer data block for transmission has full header 0b11 next upper layer data block for transmission has compressed header

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where an AMR codec mode has been changed in an upper entity associated with the state indication information.

The AMR codec used in voice communication has one or more modes which are classified according to the size of voice information data. For example, a 136-bit upper layer data block (MAC SDU) is transferred to the MAC layer every 20 ms in a narrow-band AMR 4.75 kbps mode and a 288-bit upper layer data block (MAC SDU) is transferred to the MAC layer every 20 ms in a narrow-band AMR 12.65 kbps mode. That is, when the voice AMR code operates in one mode, the AMR codec entity generates voice information of a specific size at specific time intervals. Therefore, the size of a voice information packet transferred from the upper layer to the MAC layer is constant unless the AMR codec mode is changed. Generally, a base station or a terminal selects an AMR codec mode for use taking into consideration the amount of radio resources available in a corresponding cell, the amount of transmitted data agreed between the terminal and the base station, or the state of load in the cell. The selected AMR codec mode can be reset according to the state of the cell. Accordingly, both the base station and the terminal need to be able to cope with changes of the AMR code mode.

Voice information generated through the AMR codec (i.e., voice codec) used for voice communication has special characteristics. Voice data has two patterns, one being a talk spurt period during which somebody speaks and the other being a silent period during which nobody speaks. A voice data block containing voice information is generated every 20 ms in the talk spurt period and a silent data block containing voice information is generated every 160 ms in the silent period.

When the generated voice information corresponds to the talk spurt period, the base station will set radio resources according to the characteristics of the talk spurt period in order to efficiently use radio resources. More specifically, the base station will set radio resource information allocated to the terminal at intervals of 20 ms in consideration of the fact that a voice data block is generated every 20 ms.

In this case, if the state of the terminal is changed from the talk spurt period to the silent period, a large portion of the radio resources allocated at intervals of 20 ms will not be used since the silent data block is generated every 160 ms. Accordingly, the base station needs to immediately detect that the state of the terminal has been changed to the silent period and to immediately reset radio resources, thereby preventing waste of radio resources.

Similarly, one can consider that the base station sets scheduling resources to allow the terminal to use radio resources at intervals of 160 ms according to the silent period. In this case, if the state of the terminal is changed from the silent period to the talk spurt period, voice information transmission is delayed since the amount of resources allocated to the terminal is small although the amount of voice information to be transmitted from the terminal is large. In this case, the base station also needs to immediately reset radio resource allocation information.

Therefore, state indication information suggested in another embodiment of the invention indicates whether or not a change has been made in the voice AMR codec mode or whether or not a change has been made between the talk spurt period and the silent period.

Table 2 illustrates an example of 2-bit state indication information for an event indicating whether or not a change has been made in the AMR codec mode or whether or not a change has been made between the talk spurt period and the silent period during AMR-based voice communication using a dedicated or common traffic channel according to another embodiment of the invention.

TABLE 2 STATE INDICATION INFORMATION HEADER OF CURRENT OR NEXT (2 BITS) UPPER LAYER DATA BLOCK 0b00 no change 0b01 AMR codec mode is changed 0b10 Change is made from silent period to talk spurt period 0b11 Change is made from talk spurt period to silent period

In Table 2, an example change of the AMR codec mode is a change between a narrow-band AMR 4.75 kbps mode and a narrow-band AMR 12.65 kbps mode.

A specific event for setting the state indication information suggested in another embodiment of the invention is an occasion where an upper layer data block associated with the state indication information is an urgent control message or a non-urgent control message.

Control information communicated through a Signaling Radio Bearer (SRB) for control of configuration (or setup) between a base station and a terminal can be classified into relatively urgent control information and relatively non-urgent control information. An example of the urgent control information is control information associated with a handover command received from the base station when a terminal moves between cells, and an example of the relatively non-urgent control message is control information that the base station uses to notify one or more terminals of broadcast service channel information.

In this case, when a logical channel indicated by an identifier of an upper layer data block is a channel carrying system information such as a Broadcast Control CHannel (BCCH), 1-bit state indication information can be used to indicate whether the upper layer data block that is being currently processed or will be processed next is an urgent message.

Information regarding a specific event for setting the state indication information suggested in another embodiment of the invention can be provided to each terminal through system information or traffic information communicated between the base station and the terminal. More specifically, during RB configuration or re-configuration, the base station notifies, through an RRC configuration message, the terminal of specific events that the terminal needs to check for a specific logical channel and of relations between the events and respective state indication information values, thereby allowing the terminal to perform transmission according to the notification.

Although the upper layer data block is a MAC SDU and a data block transferred to a lower layer is a MAC PDU in the above embodiments of the invention, the invention is not necessarily applied to SDUs and PDUs of the MAC layer and may be applied to SDUs and PDUs of any other layer in which the above functions can be implemented or are needed.

FIG. 5 illustrates a structure of a MAC PDU including at least one state indication information suggested in another embodiment of the invention.

A sub-header of each upper layer data block includes a first field including an LCID as an identifier of a logical channel through which the upper layer data block is received, a second field including state indication information indicating the state of the upper layer data block, the state indication information being selected variably according to the logical channel through which the upper layer data block is received, and a third field including information indicating the size of the upper layer data block. The order of arrangement of the first to third fields shown in FIG. 5 can be changed according to system situations.

FIG. 5 illustrates example usage of state indication information having one bit indicating an event associated with each upper layer data block in a MAC PDU having three upper layer data blocks carrying 3 different logical channels.

The first upper layer data block is a TCP/IP packet and uses state indication information indicating whether or not header compression has been applied.

A logical channel capable of carrying a TCP/IP packet such as a Dedicated Traffic CHannel (DTCH) or a Common Traffic Channel (CTCH) can be indicated by an LCID of “A”. Here, “A” represents a specific binary value.

That is, when the LCID is “A”, the upper layer data block is a TCP/IP packet and an event associated with the upper layer data block includes an event regarding whether a header of the TCP/IP packet is a full header or a compressed header.

The state indication information in the first sub-head indicates a “full header” when the value of the state indication information is “1” and indicates a “compressed header” when the value of the state indication information is “0”. Alternatively, the state indication information in the first sub-head can be set to indicate a “full header” when the value of the state indication information is “0” and to indicate a “compressed header” when the value of the state indication information is “1”.

When a receiving side receives an upper layer data block whose LCID is “A”, the receiving side checks state indication information to determine whether the received upper layer data block is a full header or a compressed header and allocates radio resources according to the determination to the upper layer data block or requests that the transmitting side allocate radio resources according to the determination to the upper layer data block.

The second upper layer data block is a VoIP packet and uses state indication information for discriminating between a talk spurt period and a silent period.

The upper layer data block to which VoIP is applied uses an LCID of “B” which can indicate a logical channel capable of carrying a VoIP packet. Here, “B” represents a specific binary value.

More specifically, when the LCID in the second sub-head is “B”, the state indication information in the second sub-head indicates a “talk spurt period” if the value of the state indication information is “1” and indicates a “silent period” if the value of the state indication information is “0”. Alternatively, the state indication information in the second sub-head can be set to indicate a “talk spurt period” when the value of the state indication information is “0” and to indicate a “silent period” when the value of the state indication information is “1”.

When a receiving side receives an upper layer data block with an LCID of “B” and a state indication information value of “1”, the receiving side determines that the upper layer data block corresponds to a talk spurt period and allocates radio resources according to the talk spurt period to the upper layer data block or requests that the transmitting side allocate radio resources according to the talk spurt period.

When the state indication information value is “0”, the receiving side determines that the upper layer data block corresponds to a silent period and allocates radio resources according to the silent period or requests that the transmitting side allocate radio resources according to the silent period.

In the case of VoIP services, a talk spurt period and a silent period are defined as described above. Thus, if the current state indication information is different from state indication information of a previous transmission period, the receiving side may previously perform or request allocation of radio resources corresponding to the specific talk spurt period or the specific silent period.

The third upper layer data block relates to specific control information. Control information transmitted through a Signaling Radio Bearer (SRB) for control of configuration (or setup) between a base station and a terminal or the like can be classified into relatively urgent control information such as a handover command and relatively non-urgent control information such as broadcast service channel information as described above.

Thus, in the case of an upper layer data block using a logical channel such as a BCCH, a PCCH, a DCCH, or a CCCH, it is possible to determine, through state indication information, whether or not generation of urgent control information or non-urgent control information has occurred as an event associated with the upper layer data block. In this embodiment, the state indication information indicates an urgent message if the value of the state indication information is “1” and indicates a non-urgent message if the value of the state indication information is “0”. Alternatively, the state indication information can be set to indicate an urgent message if the value of the state indication information is “0” and to indicate a non-urgent message if the value of the state indication information is “1”.

When a receiving side receives an upper layer data block with an LCID of “C” and a state indication information value of “1”, the receiving side determines that the upper layer data block corresponds to an urgent message and allocates radio resources according to the urgent message to the upper layer data block or requests that the transmitting side allocate radio resources according to the urgent message. The receiving side may perform or request processing of the upper layer data block by priority since the upper layer data block is an urgent message and may perform or request processing of the upper layer data block stronger at a physical stage since the upper layer data block is important information.

Table 3 illustrates LCIDs and state indication information values of events associated with the LCIDs according to the above embodiment of FIG. 5 in the case where 1-bit state indication information is used as described above.

TABLE 3 state indication state indication LCID information = 1 information = 0 A full header compressed header B talk spurt period silent period C urgent non-urgent

Although the state indication information in this embodiment indicates state indication information associated with an event of an upper layer data block that is being currently processed, it may serve as control information in a specific transmission period, for example, control information after or corresponding to a specific number of Transmission Time Intervals (TTIs), each of which is a basic transmission interval of a specific transport channel in the MAC layer.

FIG. 6 illustrates a MAC header of an E-UMTS suggested in another embodiment of the invention.

A sub-head of a MAC PDU of the E-UMTS includes a 5-bit LCID field, a 1-bit E field, a 2-bit R field, a 1-bit F field, and a 7-bit (possibly, 15-bit) L field. In this embodiment, a MAC PDU includes a total of N upper layer data blocks. Therefore, a header of a MAC PDU also includes a total of N MAC PDU sub-heads. Details of the LCID field, the E field, the R field, and the L field are described above with reference to FIG. 2. In this embodiment of the invention shown in FIG. 6, one bit of the 2-bit R field is used as state indication information.

Unlike sub-heads of general MAC PDUs, the sub-header of this embodiment includes a format field F indicating the size of the length field. MAC control elements may include a Buffer Status Reporting (BSR) control element, a C-RNTI control element, a DRX command control element, and the like. The BSR provides information regarding the amount of data in an uplink buffer. The SSR control element provides information regarding the size of the buffer. The C-RNTI control element represents identification information of a new terminal which has entered a cell in a control RNC. The MAC control elements may also include other control elements as needed.

Each MAC PDU is generally processed in bytes. Therefore, when a total length of a combination of a MAC header, control elements, and MAC SDUs is not in bytes, a padding field is added to give a dummy value to the combination so that the total length is in bytes.

While the above embodiments of the present invention have been described focusing on the data communication relationship between transmitting and receiving sides for ease of explanation, the transmitting side may be a terminal or a base station in a network and the receiving side may be a base station in a network or a terminal. The terms used in the present disclosure can be replaced with other terms having the same meanings. For example, the term “terminal” may be replaced with another term such as “mobile station”, “mobile terminal”, “communication terminal”, “user equipment (UE)”, or “user device” and the term “base station” may be replaced with another term such as “fixed station”, “Node B (NB)”, or “eNode B (eNB)”.

Those skilled in the art will appreciate that the present invention may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

INDUSTRIAL APPLICABILITY

The present invention can be applied to a wireless communication system, and more particularly to a method for generating data blocks in a wireless communication system. 

The invention claimed is:
 1. A method for generating a data block at a medium access control, MAC, layer of a transmitting side in a wireless communication system, the method comprising: receiving an upper layer data block from an upper layer; and generating the data block including a MAC header and a MAC payload, wherein the MAC payload comprises at least part of the upper layer data block and the MAC header comprises one or more sub-headers, wherein each of the one or more sub-headers comprises: a LCID (logical channel identifier) field being used to indicate an identifier of a logical channel through which the upper layer data block is received, a 1-bit state indication information field being used to indicate a state of the upper layer data block, wherein the 1-bit value of the state indication information field is interpreted differently according to a value of the LCID field, and a L (length) field being used to indicate a size of the at least part of the upper layer data block, wherein the state indication information field in one of the one or more sub-headers indicates whether the upper layer data block includes a full header or a compressed header when the LCID field in the same sub-header indicates the upper layer data block is received through a the logical channel related with an IP packet of the upper layer.
 2. The method according to claim 1, wherein the state indication information field in one of the one or more sub-headers further indicates whether the upper layer data block has been generated in a talk spurt period or a silent period when the LCID field in the same sub-header indicates the upper layer data block is received through a logical channel related with a voice packet.
 3. The method according to claim 1, wherein the state indication information field in one of the one or more sub-headers further indicates whether the upper layer data block is urgent information or non-urgent information when the LCID field in the same sub-header indicates the upper layer data block is received through a logical channel related with predetermined control information.
 4. The method according to claim 1, wherein the state indication information field is included in a MAC sub-header corresponding to the upper layer data block. 